-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test: fix TestTaskError and TestMultiError flaky tests (#2779) #2820
test: fix TestTaskError and TestMultiError flaky tests (#2779) #2820
Conversation
[REVIEW NOTIFICATION] This pull request has not been approved. To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: fb8ab04
|
/run-integration-tests |
@ti-chi-bot: Your PR was out of date, I have automatically updated it for you. At the same time I will also trigger all tests for you: /run-all-tests If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
Codecov Report
@@ Coverage Diff @@
## release-5.2 #2820 +/- ##
================================================
Coverage ? 56.2207%
================================================
Files ? 169
Lines ? 20713
Branches ? 0
================================================
Hits ? 11645
Misses ? 7941
Partials ? 1127 |
This is an automated cherry-pick of #2779
What problem does this PR solve?
close https://github.com/pingcap/ticdc/issues/2469
What is changed and how it works?
In one case, it did happen that isCancelled was used to the next event before it was updated, and ErrCh immediately received an error, just as cancel was called during the execution of AddEvent, which is why I encountered this unstable test. I was able to reproduce the problem occasionally after increasing the number of events and limiting resources locally.
Check List
Tests
Code changes
None
Side effects
None
Related changes
Release note